-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "Windows Install Action Fix" #2401
Conversation
…o true Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
Signed-off-by: Craig Perkins <cwperx@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you provide more details on why you would like to revert this change?
Signed-off-by: Craig Perkins <cwperx@amazon.com>
@peternied The buggy behavior that @scrawfor99 identified and fixed was being used during the distribution build to create the containers and as a result the containers created were binding by default to all network interfaces. This change reverts the change back to the expected (not necessary correct) behavior. This change is needed for 2.5.0. This PR should be followed-up with an analysis to see where these scripts are called from and to update the calls to the correct flags instead of the catchall These scripts will need another option to indicate whether the demo certs should be installed (perhaps |
@peternied I filed a bug report to describe the issue with the install_demo_configuration scripts: #2402 |
Codecov Report
@@ Coverage Diff @@
## main #2401 +/- ##
============================================
- Coverage 61.21% 61.04% -0.17%
+ Complexity 3277 3268 -9
============================================
Files 260 260
Lines 18362 18362
Branches 3249 3249
============================================
- Hits 11241 11210 -31
- Misses 5535 5563 +28
- Partials 1586 1589 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the context, net net we cannot modify the existing parameters
Note; plugin installation has passed, this file has no impact on other tests. |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-2401-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9cdaeca7e97ca4a4351a2d7bbc729db0f4a1704e
# Push it to GitHub
git push --set-upstream origin backport/backport-2401-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-2401-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9cdaeca7e97ca4a4351a2d7bbc729db0f4a1704e
# Push it to GitHub
git push --set-upstream origin backport/backport-2401-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.4 2.4
# Navigate to the new working tree
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-2401-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9cdaeca7e97ca4a4351a2d7bbc729db0f4a1704e
# Push it to GitHub
git push --set-upstream origin backport/backport-2401-to-2.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.4 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.5 2.5
# Navigate to the new working tree
cd .worktrees/backport-2.5
# Create a new branch
git switch --create backport/backport-2401-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 9cdaeca7e97ca4a4351a2d7bbc729db0f4a1704e
# Push it to GitHub
git push --set-upstream origin backport/backport-2401-to-2.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.5 Then, create a pull request where the |
@cwperks Looks like the backports will need attention |
Description
Reverts #2308 and uses
-i -c
as arguments to the windows program to make it equivalent to-y
Maintenance
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.